-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added a flag to enable human input for Bedrock Agents #289
Conversation
jdbaker01
commented
Nov 22, 2024
•
edited by 3coins
Loading
edited by 3coins
- Simplify the create of an agent which uses human input by including a flag (False by default to match current behavior).
- Add new integration test for the use case.
Will update, fixing lint. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdbaker01
This seems a bit different from the human confirmation input that your referenced in the documentation. The test sample you have included seems purely prompt based. Should the CONFIRM or DENY from the agent response be handled anywhere in the code?
That is a different feature, this enables human input if the agent doesn’t have all the parameters. The confirm/deny is a separate issue and is “human confirmation”. Confirmations can be added to individual action whereas human input is applicable to all actions and is not confirm/deny but asks for missing params. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdbaker01
Looks good!